-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix root mounts not being setup in some cases #39044
Conversation
39893f0
to
8cf7451
Compare
8cf7451
to
c3c8b78
Compare
Signed-off-by: Robin Appelman <[email protected]>
Signed-off-by: Robin Appelman <[email protected]>
c3c8b78
to
1eb3293
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've not worked on Nextcloud before, but the changes look sensible to me. I've tested this on my setup and it successfully fixed #32194.
This fixes active breakage of production systems and updates to those, the corresponding bug is already 1,5y open. |
/backport to stable27 |
/backport to stable26 |
Thanks a lot, much appreciated! |
In some cases, the root setup is triggered before the
filesystem
apps are loaded. These are then loading during the filesystem wrapper setup, if the loading of an app attempts to interact with the filesystem, it will attempt to setup the filesystem recursively.This recursion is prevented by the
SetupManager
, but that also means that the app loading code sees the filesystem with no mounts setup. Which will lead to errors.By moving the wrapper setup to before the recursion setup we can prevent this issue